home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group02b.txt
/
000109_icon-group-sender_Mon Nov 11 10:56:17 2002.msg
< prev
next >
Wrap
Internet Message Format
|
2003-01-02
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id gABHuFk09841
for icon-group-addresses; Mon, 11 Nov 2002 10:56:15 -0700 (MST)
Message-Id: <200211111756.gABHuFk09841@baskerville.CS.Arizona.EDU>
Date: Sat, 9 Nov 2002 10:17:10 -0700
From: Clint Jeffery <jeffery@cs.nmsu.edu>
To: ecashin@uga.edu
CC: icon-group@cs.arizona.edu
Subject: Re: Question about Icon
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
[Ed Cashin calls into question the solidity of my darling little language:]
> Is unicon pretty solid? I noticed that the uni.zip archive for
> version 10.0 doesn't expand into its own directory (usually a bad sign)
I am not sure you are being fair in your conclusions here, Ed. :-)
> the Install target fails with a complaint about lib/*.*
> being absent. Maybe I should give it another look, though.
Hmm, I grant that this is a sloppy oversight. I backed Icon 9.4's
Install rule into Unicon, but I disagree with their "lib" directory
organization, so Unicon uses a different one. I need to modify
the Install target to make better sense. Thanks for mentioning it.
As to whether Unicon is pretty solid, I had better let Unicon users answer
that one. It has enjoyed a long lingering beta period and is being used
by a lot of people who are doing interesting things with it.
Clint jeffery@cs.nmsu.edu